Method and system for detection of malware that connect to network destinations through cloud scanning and web reputation

ABSTRACT

A method for detecting malware includes the steps of identifying a one or more open network connections of an electronic device, associating one or more executable objects on the electronic device with the one or more open network connections of the electronic device, determining the address of a first network destination that is connected to the open network connections of the electronic device, receiving an evaluation of the first network destination, and identifying one or more of the executable objects as malware executable objects. The evaluation includes an indication that the first network destination is associated with malware. The malware executable objects includes the executable objects that are associated with the open network connections that are connected to the first network destination.

RELATED APPLICATION

This application is a Continuation of U.S. patent application Ser. No.12/694,988 filed Jan. 27, 2010, which is incorporated herein byreference in its entirety.

TECHNICAL FIELD OF THE INVENTION

The present invention relates generally to computer security and malwareprotection and, more particularly, to a method and system detectingmalware that connect to network destinations outside of an infectedmachine, through cloud scanning and web reputation.

BACKGROUND

Server side polymorphism is a difficult challenge when creatinganti-virus techniques. In server side polymorphism, a malware servergenerates different permutations of the same binary. The permutatedversion is then downloaded by a client side malware deployed on aninfected end point. The new permutations version is used for furtherpropagation, as anti-virus software may not yet recognize the newpermutated version. To make contact with the server to download the newmutated version, the client side malware must use an unsuspectingcomputer's network connection. A server may unsuspectingly host thepermutated malware to be downloaded, as it may have been commandeered bya malware server.

Other kinds of malware also need to “phone home” to a server as well.For example, downloaders may contact a server to download other binariesto initiate or continue attacks. Spyware, password stealers, and thelike must contact a server to upload collected data. Some malware mustcontact a server in order to let an attacking process take control ofthe infected machine.

Malware may include the varieties described above. Malware may alsoinclude, but is not limited to, sources of spam, sources of phishingattacks, sources of denial-of-service-attacks, viruses, loggers,Trojans, adware, or any other digital content that produces unwantedactivity.

SUMMARY

A method for detecting malware includes the steps of identifying one ormore open network connections of an electronic device, associating oneor more executable objects on the electronic device with the one or moreopen network connections of the electronic device, determining theaddress of a first network destination that is connected to the opennetwork connections of the electronic device, receiving an evaluation ofthe first network destination, and identifying one or more of theexecutable objects as malware executable objects. The evaluationincludes an indication that the first network destination is associatedwith malware. The malware executable objects includes the executableobjects that are associated with the open network connections that areconnected to the first network destination.

In a further embodiment, an article of manufacture includes a computerreadable medium and computer-executable instructions. Thecomputer-executable instructions are carried on the computer readablemedium. The instructions are readable by a processor. The instructions,when read and executed, cause the processor to identify a one or moreopen network connections of an electronic device, associate one or moreexecutable objects on the electronic device with the one or more opennetwork connections of the electronic device, determine the address of afirst network destination that is connected to the open networkconnections of the electronic device, receive an evaluation of the firstnetwork destination, and identify one or more of the executable objectsas malware executable objects. The evaluation includes an indicationthat the first network destination is associated with malware. Themalware executable objects comprise the executable objects that areassociated with the open network connections that are connected to thefirst network destination.

In a further embodiment, a method of evaluating the reputation of anetwork destination includes the steps of receiving information about anetwork destination from a monitor, accessing reputation informationabout the network destination in a reputation database, evaluatingwhether reputation information indicates that the network destination isassociated with malware, and sending the evaluation to the monitor. Themonitor is scanning an electronic device for malware. The networkdestination is in communication with an executable object on theelectronic device.

In a further embodiment, an article of manufacture includes a computerreadable medium and computer-executable instructions. Thecomputer-executable instructions are carried on the computer readablemedium. The instructions are readable by a processor. The instructions,when read and executed, cause the processor to receive information abouta network destination from a monitor, access reputation informationabout the network destination in a reputation database, evaluate whetherreputation information indicates that the network destination isassociated with malware, and send the evaluation to the monitor. Themonitor is scanning an electronic device for malware. The networkdestination is in communication with an executable object on theelectronic device.

In a further embodiment, a system for detection of malware includes amonitor and a reputation application. The monitor is configured toidentify one or more open network connections of an electronic device,identify one or more executable objects on the electronic device usingthe one or more open network connections of the electronic device, anddetermine the address of a first network destination that is connectedto the one or more open network connections of the electronic device.The reputation application configured to receive information about thefirst network destination from the monitor, access reputationinformation about the first network destination in a reputationdatabase, evaluate whether reputation information indicates that thefirst network destination is associated with malware, and return theevaluation to the monitor. The monitor is further configured to receivean evaluation of the first network destination, and determine one ormore malware executable objects. The evaluation includes an indicationthat the first network destination is associated with malware. The oneor more malware executable objects comprise the executable objects incommunication with the first network destination evaluated to beassociated with malware.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention and itsfeatures and advantages, reference is now made to the followingdescription, taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 is an illustration of an example system for defeating malwarethat communicate with network servers through connection scanning andweb reputation;

FIG. 2 is an illustration of some portions of the system of FIG. 1 forscanning an electronic device;

FIG. 3A is an illustration of example information that may be sharedbetween a monitor and a reputation server concerning networkdestinations connected to an electronic device.

FIG. 3B is an illustration of example information that may be sharedbetween a monitor and a reputation server concerning networkdestinations connected to an electronic device and associated with anapplication which in turn is associated with malware.

FIG. 4 is an illustration of an example reputation server for trackingthe reputation of network destinations according to the networkdestinations' propensity to host malware;

FIG. 5 is an illustration of example method to detect malware thatcontact a network destination from an electronic device; and

FIG. 6 is an illustration of example method to evaluate networkdestinations as to their association with malware.

DETAILED DESCRIPTION

FIG. 1 is an illustration of an example system 100 for defeating malwarethat communicate with network servers through connection scanning andweb reputation. System 100 may comprise a monitor 102, an electronicdevice 104, and a reputation server 108. Monitor 102 may be configuredto scan electronic device 104 for possible malware that communicate withnetwork destinations 106 to carry out malicious activities. Monitor 102may be configured to communicate with reputation server 108 to determinewhether applications or network connections belonging to electronicdevice 104, or network destinations 106 connected through network 112 toelectronic device 104, comprise malware or malicious activitiesassociated with malware. Reputation server 108 may be configured toevaluate the network connections, and monitor 102 may be configured toreceive the evaluation from reputation server 108.

In one embodiment, monitor 102 may be configured to operate in a cloudcomputing scheme. Monitor 102 may comprise software that resides onnetwork 110, and may be loaded and executed on a machine in network 110.Monitor may be communicatively coupled to electronic device 104 throughnetwork 110 or any other suitable network or communication scheme.Monitor may scan electronic device 104 without executing on electronicdevice 104. Monitor 102 may be communicatively coupled to reputationserver 108 through network 110, network 114, or both. The reputationserver 108 may comprise a server on network 114. In one embodiment,monitor 102 and reputation server 108 may reside on the same network. Inone embodiment, monitor 102 and reputation server 108 may reside on thesame hardware.

In one embodiment, monitor 102 may reside on electronic device 104.Monitor 102 may be loaded and executed on electronic device 104. Monitor102 may be communicatively coupled to reputation server 108 throughnetwork 114, or any other suitable network or communication scheme.

Networks 110, 112, 114 may comprise any suitable networks forcommunication between electronic device 104, monitor 102, networkdestinations 106, and reputation server 108. Such networks may includebut are not limited to: the Internet, an intranet, wide-area-networks,local-area-networks, back-haul-networks, peer-to-peer-networks, or anycombination thereof.

Electronic device 104 may comprise any device configurable to interpretand/or execute program instructions and/or process data, including butnot limited to: a computer, desktop, server, laptop, personal dataassistant, or smartphone.

FIG. 2 is an illustration in further detail of some portions of thesystem 100 for scanning an electronic device 104. Electronic device 104may comprise a processor 202 coupled to a memory 204, a network device206, and one or more applications 208. Monitor 102 may reside onelectronic device 104, or on any other electronic device, server, orother suitable mechanism to scan electronic device 104 for possiblemalware that communicate with network destinations 106 to carry outmalicious activities. Monitor 102 may comprise any application, process,script, module, executable, server, executable object, library, or othersuitable digital entity. Monitor 102 may be communicatively coupled toreputation server 108 over network 114. Monitor 102 may be configured toreside in memory 204 for execution by processor 202 with instructionscontained in memory 204.

Processor 202 may comprise, for example a microprocessor,microcontroller, digital signal processor (DSP), application specificintegrated circuit (ASIC), or any other digital or analog circuitryconfigured to interpret and/or execute program instructions and/orprocess data. In some embodiments, processor 202 may interpret and/orexecute program instructions and/or process data stored in memory 204.Memory 204 may be configured in part or whole as application memory,system memory, or both. Memory 204 may include any system, device, orapparatus configured to hold and/or house one or more memory modules.Each memory module may include any system, device or apparatusconfigured to retain program instructions and/or data for a period oftime (e.g., computer-readable media).

Network device 206 may be a virtual or actual device. Network device 206may be configured to, among other things, communicate between electronicdevice 104 and one or more other electronic devices, software, servers,or networks, such as network 112 or network destinations 106. Networkdevice 206 may comprise one or more inbound network ports 206 a forreceiving communications and or more outbound networked ports 206 b forsending communications. Network device 206 may comprise any suitablecombination of hardware and/or software to establish communication withelectronic device 104 over a network. In one embodiment, network device206 may be coupled externally to electronic device 104. One or moreapplications 106 may be coupled or connected to network device 206, andaccordingly use network device 206 to accomplish communication tasks.Network device 206 may be configured to facilitate any suitablecommunications protocol to conduct communications for electronic device104 or applications 208 over a network.

Applications 208 may be an application configured to operate onelectronic device 104. Applications 208 may be configured to reside inmemory 204 for execution by processor 202 with instructions contained inmemory 204. Applications 208 may be of any kind of digital entitysuitably configured for operation on electronic device 104. Applications208 may comprise, but are not limited to, a program, process,executable, application, driver, operating system, module, source code,object code, meta-code, shared library, system executable object,script, object file, or a combination of these elements. Applications208 may be coupled to network device 206. Applications 208 may becommunicatively coupled to network device 206. Applications 208 may makeuse of network device 206 through any suitable method. Monitor 102 maybe configured to determine in part whether applications 208 comprisemalware. In one embodiment, monitor 102 may be configured to determinewhether applications 208 comprise malware that communicates with amalware server.

Network destinations 106 may comprise websites, servers, machines,processes, applications, or other entities residing on a network 112.Network destinations 106 may be communicatively coupled to electronicdevice 104 through network 112. Network destinations 106 may becommunicatively coupled to network device 206. Network destinations 106may be communicatively coupled to the inbound network ports 206 a and/oroutbound network ports 206 b. Network destinations 106 may becommunicatively coupled with one or more applications 208 of electronicdevice 104 through network 112, and through network device 206. Networkdestinations 106 may be identifiable through an address. In oneembodiment, the address of network destination 106 a may comprise anInternet Protocol address of 255.255.255.255. In one embodiment, theaddress of network destinations 106 may comprise a host name, domain orserver name. For example, network destination 106 b may be identified as“widget.example.com.”

Monitor 102 may be configured to determine and enumerate the opennetwork connections of network device 206. Monitor 102 may be configuredto determine the open network socket connections of network device 206.Monitor 102 may be configured to determine the open network connectionsof network device 206 when the driver for network device 206 isoperational, indicating that the network device 206 is in use. Monitor102 may be configured to determine the connection type of the opennetwork connections of network device 206. In one embodiment, monitor102 may be able to determine transport control protocol (“TCP”)connections and/or user datagram protocol (“UDP”) connections. Monitor102 may be configured to determine the direction of the open networkconnections of network device 206. In one embodiment, monitor 102 may beable to determine inbound connections at inbound network ports 206 aand/or outbound connections at outbound network ports 206 b. Monitor 102may be configured to obtain the identity of the entity at the other endof the open network connections of network device 206. In oneembodiment, monitor 102 may be configured to obtain the addresses ofnetwork destinations 106. In a further embodiment, monitor 102 may beconfigured to obtain the internet protocol (“IP”) addresses and/or hostnames of network destinations 106. Monitor 102 may be configureddetermine which applications 208 may be using the connection to networkdestinations 106.

FIG. 3A is an illustration of example information that may be sharedbetween monitor 102 and reputation server 108 concerning networkdestinations connected to electronic device 104. Monitor 102 may beconfigured to compile a table 302 of the network destinations, and foreach the applications 306 associated with the network destinations, theprotocol 308 used for each connection, the socket and/or port 310 usedfor each connection, the network destinations' addresses 312, thenetwork destinations' host names 314, and/or whether the ports areinbound or outbound 316.

The specific values shown in FIG. 3A are for illustration purposes only.For example, APP1 208 a may have an inbound network connection to thenetwork destination “example1.com” 106 a, of type TCP, on port 1, withthe host name example1.com. APP2 208 b may have an outbound networkconnection to the network destination “server.example2.com” 106 b, oftype TCP, on port 2, with the host name server.example2.com and the IPaddress 222.222.222.222. APP3 208 c may have an inbound networkconnection to the network destination “255.255.255.255” 106 c, of typeTCP, on port 3, with the IP address 255.255.255.255. APP1 208 a may alsohave an outbound network connection to the network destination“example3.com” 106 d, of type TCP, on port 4, with the host nameexample3.com and the IP address 444.444.444.444. APP2 208 b may alsohave an inbound network connection to the network destination“example4.com” 106 e, of type UDP, on port 5, with the host nameexample4.com and the IP address 555.555.555.555. Although particularinformation and formats are shown are illustrated in FIG. 3A, anysuitable information and format may be exchanged between monitor 102 andreputation server 108.

Referring back to FIG. 2, monitor 102 may be configured to communicatewith reputation server 108 to determine the reputation of networkdestinations 106. Monitor 102 may be configured to receive an evaluationof network destinations 106 from reputation server 108. Reputationserver 108 may be configured to determine whether a given networkdestination 106 is known to host malware or not. Monitor 102 may beconfigured to send the information of table 302 of network destinations,or additional information regarding the applications 208 of electronicdevice, to reputation server 108. Monitor 102 may be configured to sendsuch information reputation server 108 with an initial query concerningnetwork destinations 106, if reputation server 108 determines thatnetwork destinations 106 may be known to host malware, and/or uponrequest from reputation server 108.

Monitor 102 may be configured to protect electronic device 104 based oninformation that one or more network destinations 106 are known to hostmalware. Monitor 102 may be configured to protect electronic device 104in any way suitable to prevent malware associated with networkdestinations 106 known to host malware, or with applications connectingto network destinations 106 known to host malware, from affectingelectronic device 104. Monitor 102 may be configured to protectelectronic device 104 directly, through active or passive methods.Monitor 102 may be configured to make use of, configure, and/orcommunicate with other processes, devices, applications, or entities onor with access to electronic device 104 to protect electronic device104. In one embodiment, monitor 102 may be configured to block access tonetwork destinations 106 known to host malware.

In one embodiment, monitor 102 may be configured to clean electronicdevice 104 of applications 208 connected to a network destination knownto host malware. Monitor 102 may be configured to clean electronicdevice of malware hosted by network destination 106. Execution ofmalware hosted by network destination 106 may be blocked, quarantined orremoved. Monitor 102 may be configured to undo modifications toelectronic device 104 made in relation to malware. Monitor 102 may beconfigured to monitor the behavior of applications 208 connected to anetwork destination 106 hosting malware. In one embodiment, monitor 102may be configured to analyze the network connections utilized byapplications 208. Monitor 102 may be configured to clean, quarantine, orotherwise neutralize electronic device 104 of applications 208 that wereconnected to a network destination 106 determined to have hostedmalware. Monitor 102 may be configured to send an alert or message to auser or administrator of electronic device 104 requesting permission toconduct any protective act.

In another embodiment, monitor 102 may be configured to protectelectronic device 104 by applying behavioral rules to the operation ofapplications 208. A behavioral rule may comprise one or more rules thatdescribe symptoms of suspicious activity of an active and runningprocess or application. Behavioral rules may be used by a monitoringapplication to continuously monitor the behavior of a process to observewhether it exhibits the behavior described in the rule. Monitor 102 maybe configured to receive a behavioral rule from reputation server 108. Abehavioral rule may be of any form suitable to associate malware with anaction of an application on electronic device 104. A behavioral rule maycomprise a module, functional library, shared library, and/or othersuitable mechanism.

If one or more applications 208 have connected to a network destination106 known to host malware, monitor 102 may be configured to enumeratethe open network connections owned by the one or more applications 208.Monitor 102 may be configured to determine the socket for each suchconnection, other identifying information such as protocol andconnection type, and the identity of any network destinations 106 towhich applications 208 are connected.

FIG. 3B is an illustration of example information that may be sharedbetween monitor 102 and reputation server 108 concerning networkdestinations connected to electronic device 104 and associated with anapplication which in turn is associated with malware. Monitor 102 may beconfigured to summarize such information as shown in FIG. 3B, or in anyother suitable format. Although particular information and formatting isillustrated in FIG. 3B, any suitable information and format can beexchanged between monitor 102 and reputation server 108. Suchinformation may comprise a table 320 of related suspicious connections.Table 320 of related suspicious connections may comprise the identity ofthe application 324 related to malware hosted on a network destination,and identify all open connections for such application 324. Table 320 ofrelated suspicious connections may also comprise the network address 312of network destinations connected to application 324. In addition, table320 of related suspicious connections may comprise the host name 314 ofnetwork destinations connected application 324. Furthermore, table 320of related suspicious connections may include any information suitableto identify the operations of a network connection of or networkdestination connected to an application 324 related to malware. Monitor102 may be configured to transmit the information contained in table 320of related suspicious connections to reputation server 108.

FIG. 4 is an illustration of an example reputation server 108 fortracking the reputation of network destinations according to the networkdestinations' propensity to host malware. Reputation server 108 maycomprise a reputation server application 402, a reputation database 404,and a processor 406 coupled to a memory 408. Reputation serverapplication 402 may be configured to communicate with monitor 112 andreputation database 404 to track network destinations to determinewhether the network destinations are known to host malware.

Reputation server application 402 may comprise any application, process,script, module, executable, server, executable object, library, or otherdigital entity suitable to interface with monitor 102 and reputationdatabase 404 to track the reputation of network destinations accordingto the network destination's propensity to host malware. Reputationserver application 402 may reside on reputation server 108, or on anyother suitable server to track the reputation of network destinationsaccording to the network destination's propensity to host malware.Reputation server application 402 may be communicatively coupled tomonitor 102. In one embodiment, reputation server application 402 may becommunicatively coupled to monitor 102 over network 114. Reputationserver application 402 may be communicatively coupled to reputationdatabase 404. In one embodiment, application 402 may be communicativelycoupled to reputation database 102 over network 114. In one embodiment,reputation server application 402 and monitor 102 may be co-locatedwithin the same device, application, server, or process. In oneembodiment, reputation server application 402 and monitor 102 maycomprise functions, modules, libraries, or portions of the sameapplication, server, or process. In such an application, some featuresor functions of reputation server application 402 and monitor 102 may beredundant, and thus combined. Reputation server application 402 may beconfigured to perform particular functions or configurations of monitor102, and vice-versa, where possible. In one embodiment, monitor 102 maybe configured to reside on reputation server 108, in memory 408 forexecution by processor 406 with instructions contained in memory 408.

Processor 406 may comprise, for example a microprocessor,microcontroller, digital signal processor (DSP), application specificintegrated circuit (ASIC), or any other digital or analog circuitryconfigured to interpret and/or execute program instructions and/orprocess data. In some embodiments, processor 406 may interpret and/orexecute program instructions and/or process data stored in memory 408.Memory 408 may be configured in part or whole as application memory,system memory, or both. Memory 408 may include any system, device, orapparatus configured to hold and/or house one or more memory modules.Each memory module may include any system, device or apparatusconfigured to retain program instructions and/or data for a period oftime (e.g., computer-readable media).

Reputation server application 402 may be configured to receiveinformation from monitor 102 concerning one or more open networkconnections of electronic device 104. Information from monitor 102concerning open network connections of electronic device 104 maycomprise the identities of one or more network destinations. Reputationserver application 402 may be configured to access data contained withinreputation database 404 to determine whether or not the networkdestination is known to host malware. In one embodiment, reputationserver application 402 may receive a specific indication from reputationdatabase 404 that a particular network destination is known to hostmalware. In one embodiment, reputation server application 402 mayreceive information from reputation database 404 about a particularnetwork destination's propensity to host malware, which reputationserver application 402 must use to determine whether to indicate tomonitor 102 that the particular network destination is safe, unsafe,and/or known to host malware. Reputation server application 402 may beconfigured to indicate to monitor 102 whether one or more particularnetwork destinations are known to host malware.

Reputation server application 402 may be configured to populateinformation in reputation database 404 based upon information receivedfrom monitor 102. Reputation server application 402 may be configured topopulate reputation database 404 with information associated with aparticular network destination, such as that in table 302 of the networkdestinations, including: the applications 306 associated with eachnetwork destinations, the protocol 308 used for each connection, thesocket and/or port 310 used for each connection, the networkdestinations' addresses 312, the network destinations' host names 314,and/or whether the ports are inbound or outbound 316. Reputation serverapplication 402 may be configured to request some or all of suchinformation from monitor 102.

If no entry for a given network destination exists in reputationdatabase 404, reputation server application 402 may be configured tocreate an entry for the given network destination in reputation database404. Reputation server application 402 may be configured to give a newentry in reputation database 404 default values. Reputation serverapplication may be configured to associate a new entry in reputationdatabase 404 with an existing entry.

Reputation server application 402 may be configured to receiveinformation from monitor 102 regarding additional network destinationsassociated with network destinations known to host malware, such asthose found on a table 320 of related suspicious connections. Table 320of related suspicious connections may be configured to indicate that agiven application 324 on an electronic device, wherein the application324 was found to be connected to a network destination associated withmalware, may have had connections with additional network destinations.The additional network destinations may comprise destinations that arealso associated with malware. Reputation server application 402 may beconfigured to populate reputation database 404 with the information fromtable 320 of related suspicious connections. For a given applicationindicated in table 320 of related suspicious connections, reputationserver application 402 may be configured to indicate in reputationdatabase 404 that two network destinations may be associated. In oneembodiment, reputation server application 402 may be configured toupdate an entry in reputation database 404 that a particular networkdestination is associated with the malicious network destination. In oneembodiment, reputation server application 402 may update reputationdatabase 404 with information that a network destination may hostmalware, wherein the network destination is associated with othernetwork destinations that host the malware.

Reputation database 404 may comprise information associating one or morenetwork destinations and the network destinations' propensity to beassociated with or host malware. Reputation database 404 may beconfigured to be accessible to provide such information. In oneembodiment, reputation database may be configured to be accessible byuse of database queries from reputation server application 402.Reputation database 404 may reside on reputation server 108. Reputationdatabase 404 may reside in memory 408, or another such memory.Reputation database 404 may be configured in any manner suitable forproviding information associating one or more network destinations andthe network destinations' propensity to be associated with or hostmalware. Reputation database 404 may be implemented in a database, file,record, module, library, or any other suitable mechanism. Reputationdatabase 404 may contain any number of entries 416-428 for variousnetwork destinations. Reputation database 404 may comprise one or morecategorizations, classifications and/or evaluations of a particularnetwork destination or group of network destinations in regards to thedestination's association with malware. In one embodiment, each entry inreputation database 404 may contain a domain field 410, a reputationscore field 412, and/or one or more fields for other information 414.

Domain field 410 may be configured to indicate the network destinationor group of network destinations for which data is stored in reputationdatabase 404. In one embodiment, domain field 410 may comprise theinternet address, or internet address range of a domain, host, or othernetwork destination. In one embodiment, domain field 410 may comprisethe name of a universal resource locator (“URL”), domain, subdomain,host, or other network destination.

Reputation score field 412 may comprise a reputation score for thedomain indicated in domain field 410. A reputation score may indicate aquantitative rating of the soundness of the host in terms of a lack ofunwanted or malicious behavior. A reputation score may be calculated andmaintained by any acceptable way for determining the soundness of adomain in terms of a lack of unwanted or malicious behavior. Manyfactors may be used to determine reputation score, including but notlimited to: whether the domain is a source of spam messages; whether thedomain is the destination of links contained in spam messages; whetherthe domain is the destination of links contained is electronic messagesthat in turn contain malware; whether the domain is linked to by otherdomains or servers that hose malware; the frequency and volume ofelectronic messages or traffic to or from the domain; the destination orsource of electronic messages or traffic to or from the domain; thereputation of other domains hosted on the same servers or network as thedomain; whether the domain's content is malware-free; whether the sitehost of the domain is deviating from known historical behavior; whetherthe domain is accessed by applications connecting to domains with badreputation; or whether the domain appears on a blacklist (indicatingmalicious sites) or a whitelist (indicating safe sites). The entries inreputation score field 412 may change as new information is used topopulate reputation database 404. In one embodiment, the value ofreputation score field 412 may range from 0 to 100, wherein 0 indicatesthe least degree of trustworthiness, and 100 indicates the greatestdegree of trustworthiness of the domain. In one embodiment, a new entryinto reputation database 404 without an existing reputation is assigneda 0 for its reputation score. In one embodiment, a default entry such as“*” 430 may have a reputation score of 0.

Reputation database 404 may comprise one or more fields for otherinformation 414. Fields 414 may comprise information regarding variousfactors contributing to reputation score 412. In one embodiment, field414 may comprise information with regards to a related domain, whereinthe database entry is associated, by way of a common application runningon an electronic device, to another entry in reputation database 404.

In one embodiment, reputation database 404 may comprise a fieldindicating whether or not a domain is associated with malware. In suchan embodiment, reputation database 404 may comprise a binaryrepresentation that a domain is associated with malware. In oneembodiment, reputation database 404 may comprise a field indicating oneor more kinds of malware that a domain is associated with.

Reputation server application 402 may be configured to query reputationdatabase 404 to receive information about a particular networkdestination. In one embodiment, reputation database 404 may beconfigured to return a reputation score 412 for a particular domain 410,wherein the domain 410 corresponds to the network destination that wasqueried. In one embodiment, reputation database 404 may be configured toreturn a binary indication that the domain 410 is associated withmalware. In one embodiment, reputation database 404 may be configured toreturn an indication of the kind of malware with which the domain 410 isassociated. Reputation server application 402 may be configured tointerpret the results of the query from reputation database 404. In oneembodiment, reputation server application 402 may be configured tointerpret a reputation score 412 from reputation database 404. In suchan embodiment, reputation server application 402 may be configured toapply a threshold to a reputation score 412. For example, reputationserver application 402 may be configured to determine that a domain 410with a reputation score 412 of less than 80 may be deemed as associatedwith malware, for the purposes of the present disclosure. Reputationserver application 402 may be configured so as to minimize falsepositive identifications of applications connected to networkdestinations associated with malware. In one embodiment, reputationserver application 402 may be configured to determine that a domain 410with a reputation score 412 of less than 5 may be deemed as associatedwith malware, for the purposes of the present disclosure. In oneembodiment, reputation server application 402 may be configured todetermine that if a domain 410 is associated with a particular kind ofmalware as indicated by reputation database 404, then the domain may bedeemed as associated with malware as according to the presentdisclosure.

In operation, in FIG. 1 a monitor 102 may be operating to scanelectronic device 104 for possible malware that communicate with networkdestinations 106 to carry out malicious activities. Monitor 102 maycommunicate with reputation server 108 to determine whether applicationsor network connections belonging to electronic device 104, or networkdestinations 106 connected through network 112 to electronic device 104comprise malware or malicious activities associated with malware.

In one embodiment, monitor 102 may be running on a cloud computingscheme. In another embodiment, monitor 102 may be operating on a machinein network 110. In yet another embodiment, monitor 102 may be operatingon electronic device 104. In still yet another embodiment, monitor 104may be operating on a machine in network 114. In one embodiment,reputation server 108 may be running on a machine in network 114. In afurther embodiment, reputation server 108 and monitor 104 may be runningon the same machine.

In operation (and referring to FIGS. 1-4 collectively), one or moreapplications 208 may be running on electronic device 104. One or moreapplications 208 may be communicating with one or more networkdestinations 106 through network device 206. The network device 206 maybe operational. Monitor 102 may determine and enumerate the open networkconnections of network device 206 for network device 206. Monitor 102may determine the connection type, the direction of the connection, theIP addresses and/or host names of network destinations 106, and/or whichapplications 208 are using the connection.

Monitor 102 may compile table 302 of the network destinations, and foreach the applications 306 associated with each network destinations, theprotocol 308 used for each connection, the socket and/or port 310 usedfor each connection, the network destinations' addresses 312, thenetwork destinations' host names 314, and/or whether the ports areinbound or outbound 316.

Monitor 102 may communicate some parts of table 302 of the networkdestinations to reputation server 108 to determine the reputation ofnetwork destinations 106. Monitor 102 may be configured to sendadditional information concerning network destinations 106 or theapplications 208 of electronic device 104 if reputation server 108determines that network destinations 106 may be known to host malware,and/or upon request from reputation server 108.

Reputation server 108 may receive table 302 of the network destinations.Reputation server application 402 may be running on reputation server108. Reputation server application 402 may receive table 302 of thenetwork destinations. Reputation server application 402 may access datacontained within reputation database 404 to determine whether or not thenetwork destinations of table 302 of network destinations is known tohost malware. Reputation server application 402 may query reputationdatabase 404 to obtain the reputation score 412 of each networkdestination. For example, in reputation database 404, “example1.com” 416may have a reputation score of 4; “server.example2.com” 418 may have areputation score of 34; “255.255.255.255” 420 may have a reputationscore of 95; “example3.com” 422 may not yet exist, or may not have areputation score; “example4.com” 424 may not yet exist, or may not havea reputation score; all addresses within the subdomain “255.255.255.*”426 may have a reputation score of 40; and “example5.com/example.html”426 may have a reputation score of 90.

Reputation server application 402 may interpret the results fromreputation database 404 to determine whether the network destinationsare known to be associated with malware. In one embodiment, reputationserver application 402 may determine that one or more networkdestinations have an unacceptably low reputation score. In oneembodiment, reputation server application 402 may apply a reputationscore threshold of 80, below which it may determine the networkdestination is known to be associated with malware. For example,reputation server application 402, using a reputation score threshold of80, may determine that “example1.com” and “server.example2.com” aremalware hosts. Reputation server application 402 may determine that“255.255.255.255” poses no threat. Reputation server application 402 maycommunicate to monitor 102 that “example1.com” and “server.example2.com”are malware hosts.

Monitor 102 may receive the evaluation of network destinations 106 fromreputation server 108. Monitor 102 may protect electronic device 104based on information that one or more network destinations 106 are knownto host malware. Monitor 102 may protect electronic device 104 directly,through active or passive methods. In one embodiment, monitor 102 mayblock access to network destinations 106 known to host malware. Monitor102 may clean electronic device 104 of applications 208 connected to anetwork destination 106 known to host malware. For example, APP1 208 amay be connected to example1.com 106 a. Information received fromreputation server 108 may indicate that example1.com 106 a is a host formalware. Thus, monitor 102 may treat APP1 208 a like malware. In oneembodiment, monitor 102 may diagnose an application, such as APP1 208 a,as malware by its connection to a network destination with a knownassociation with malware, such as example1.com 106 a. For example,monitor 102 may clean electronic device 104 of APP1 208 a and APP2 208b. Monitor 102 may undo modifications to electronic device 104 made inrelation to malware of a network destination 106 or one or morediagnosed applications 208, such as APP1 208 a. Monitor 102 may monitorthe behavior of one or more applications 208 connected to a networkdestination 106 hosting malware. Monitor 102 may send an alert ormessage to a user or administrator of electronic device 104 requestingpermission to conduct any protective act.

If one or more applications 208 have connected to a network destination106 known to host malware, monitor 102 may enumerate the other opennetwork connections owned by one or more applications 208. Monitor 102may determine the socket for each such connection, other identifyinginformation such as protocol and connection type, and the identity ofany network destinations 106 to which one or more applications 208 areconnected. Monitor 102 may summarize such information as shown in FIG.3B in a table 320 of related suspicious connections. Table 320 ofrelated suspicious connections may contain the identity of theapplication 324 related to malware hosted on a network destination, andidentify all open connections for such application 324. For example,APP1 208 a and APP2 208 b may have been determined to be connected tonetwork destinations hosting malware. Thus, table 320 of relatedsuspicious connections may enumerate the other network destinations towhich APP1 208 a and APP2 208 b are connected. APP1 208 a may beconnected to “example1.com” 106 a and to “example3.com” 106 d. APP2 208b may be connected to “server.example2.com” 106 b and to “example4.com”106 d. Monitor 102 may transmit the information contained in table 320of related suspicious connections 324 to reputation server 108. In oneembodiment, monitor 102 may transmit such information with the originalsubmission of table 304 of network destinations. In one embodiment,reputation server application 402 may be able to determine suchinformation with table 304 of network destinations. In one embodiment,table 320 of related suspicious connections may also comprise the actualbinaries, files, or other data downloaded from the network destination106, or the actual binaries of applications 208 connected to a networkdestination 106 known to host malware. Monitor 106 may submit such datato the reputation server 108.

Reputation server application 402 may populate information in reputationdatabase 404 based upon information received from monitor 102.Reputation server application 402 may populate reputation server 404with information from table 304 of network destinations, and/or withinformation from in a table 320 of related suspicious connections.Reputation server application 402 may request some or all of suchinformation from monitor 102. If no entry for a given networkdestination existed in reputation database 404, reputation serverapplication 402 may create an entry for the given network destination inreputation database 404, and reputation server 108 may begin trackingthe reputation of the network destination. Reputation server application402 may update a reputation score 412 for an entry which was reported bymonitor 102 as connected to by one or more applications 208 which alsoconnected to a network destination 106 known to host malware. In oneembodiment, reputation server application 402 may indicate in reputationdatabase 404 the association between two such network destinations. Forexample, monitor 102 may have determined that APP1 208 a may haveconnected to a malware network destination such as example1.com 106 a,and also to a network destination such as example3.com, for which thereis no known association with malware. In one embodiment, reputationserver application 402 may update the reputation score 412 of“example3.com” in reputation database 404 with the same reputation as“example1.com.” In one embodiment, reputation server application 402 mayindicate in a field 414 that the entry for “example3.com” is linked to“example1.com.” Similarly, reputation sever application 402 mayindicated in a field 414 that the entry for “example4.com” is linked to“server.example2.com.” Reputation database 404 may recalculate thereputation score for entries that are associated with other entriesknown to host malware.

Reputation server application 402 may create a behavioral rule forapplication on electronic device 104. The behavioral rule may identifyall applications, binaries, and content found by monitor 102 to beconnecting to a network destination known to host malware as malware.The behavioral rule may be transmitted to and applied by monitor 102, orany another suitable application. The behavioral rule may indicate thatan application will access polymorphic servers, such as those networkdestinations known to be associated with malware.

FIG. 5 is an illustration of example method 500 to detect malware thatcontact a network destination from an electronic device. In step 510,the resources of an electronic device may be scanned for open networkconnections. Open network connections may provide communication betweenone or more applications on the electronic device to one or more networkdestinations. In step 515, the one or more network destinationsconnected to the electronic device may be determined. In step 520, theone or more applications in communication with the one or more networkdestinations may be determined. Information associated with eachdestination, and with the connection, may be collected, including butnot limited to: the applications associated with each networkdestinations, the protocol used for each connection, the socket and/orport used for each connection, the network destinations' addresses, thenetwork destinations' host names, and/or whether the ports are inboundor outbound.

In step 525, information about the detected network destinations and/orthe connections to the electronic device may be sent to a reputationserver. The information may comprise the information collected asdescribed above. In step 530, an evaluation may be received from thereputation server. The evaluation may comprise a determination ofwhether a given network destination is known to be associated withmalware. In step 535, any applications that are in communication with anetwork destination evaluated to be associated with malware may bediagnosed as malware. In step 540, the diagnosed malware applicationsmay be cleaned from the electronic device. Any appropriate step toprotect the electronic device from the diagnosed malware application, orfrom the network destinations evaluated to be associated with malware,may be taken. In one embodiment, the user or administrator of theelectronic device may be queried as to what action should be taken. Inone embodiment, the activity of a diagnosed malware application may bemonitored.

In step 545, other network destinations that are connected to diagnosedmalware applications may be identified. The other network destinationsmay comprise a network destination associated with malware. Informationabout such network destinations, including the link to the diagnosedmalware application and/or network destination associated with malwaremay be collected. In step 550, the reputation system may be informedabout the other network destinations that may comprise a networkdestination associated with malware, along with any related information.

FIG. 6 is an illustration of example method 600 to evaluate networkdestinations as to their association with malware. In step 610, anetwork destination to be evaluated may be received from a monitor, themonitor scanning an electronic device. In step 615, a reputationdatabase containing information about various network destinations maybe queried regarding the network destination to be evaluated. In step620, a response from the reputation database may be received. In oneembodiment, the response from the reputation database may comprise areputation score. In one embodiment, the response from the reputationdatabase may be an indication that the network destination is associatedwith malware. In one embodiment, the response from the reputationdatabase may be an indication that the network destination is associatedwith a particular kind of malware.

In step 625, the response from the reputation database may beinterpreted to determine whether the network destination is associatedwith malware. In one embodiment, a reputation score may be compared to athreshold score, above or below which the network destination may bedetermined to be associated with malware. In a further embodiment, sucha threshold may be 80, and values below which represent networkdestinations associated with malware. In one embodiment, an indicationthat the network destination is associated with a particular kind ofmalware may be interpreted as meaning that the network destination isassociated with malware. In step 630, the evaluation may be sent to themonitor.

In step 635, information may be received from the monitor concerningwhether any additional network destinations were associated with thenetwork destination previously evaluated as associated with malware. Anevaluation that a network destination was associated with malware mayindicate that other network destinations, communicating with the sameapplication on the electronic device, are also associated with malware.In one embodiment, such information may be received with the initialreception of network destinations to be evaluated. In one embodiment,such information may be received after a network destination has beenevaluated as associated with malware. In one embodiment, suchinformation may be received upon a request to the monitor.

In step 640, the reputation database may be populated with informationreceived from the monitor. In one embodiment, the reputation databasemay be populated with information from the monitor concerning additionalnetwork destinations that are associated with previously evaluatednetwork destinations. In a further embodiment, the previously evaluatednetwork destinations were evaluated as associated with malware. In oneembodiment, an entry in the reputation database may be populated with anindication of a link to another entry. In one embodiment, the reputationdatabase field for reputation score may recalculated based upon newinformation populated into the reputation database. In one embodiment, anew entry may be created for a network destination previouslyunaccounted for in the reputation database. In one embodiment, anadditional network destination with an association with a malwarenetwork destination may be given a reputation score of the associatedmalware network destination.

Methods 500 and 600 may be implemented using the system of FIGS. 1-4, orany other system operable to implement methods 500 and 600. As such, thepreferred initialization point for methods 500 and 600 and the order ofthe steps comprising methods 500 and 600 may depend on theimplementation chosen. In some embodiments, some steps may be optionallyomitted, repeated, or combined. In some embodiments, some steps ofmethod 500 may be accomplished in method 600, and vice-versa. In someembodiments, methods 500 and 600 may be combined. In certainembodiments, methods 500 and 600 may be implemented partially or fullyin software embodied in computer-readable media.

For the purposes of this disclosure, computer-readable media may includeany instrumentality or aggregation of instrumentalities that may retaindata and/or instructions for a period of time. Computer-readable mediamay include, without limitation, storage media such as a direct accessstorage device (e.g., a hard disk drive or floppy disk), a sequentialaccess storage device (e.g., a tape disk drive), compact disk, CD-ROM,DVD, random access memory (RAM), read-only memory (ROM), electricallyerasable programmable read-only memory (EEPROM), and/or flash memory; aswell as communications media such wires, optical fibers, and otherelectromagnetic and/or optical carriers; and/or any combination of theforegoing.

Although the present disclosure has been described in detail, it shouldbe understood that various changes, substitutions, and alterations canbe made hereto without departing from the spirit and the scope of thedisclosure as defined by the appended claims.

1. (canceled)
 2. At least one machine accessible storage medium havingcode stored thereon, the code, when executed on an electronic device, tocause the electronic device to: identify an executable file to reside inat least a portion of memory of the electronic device; provide, over anetwork, identity information of a network destination associated withthe executable file, the identity information to include a uniformresource locator (“URL”) of the network destination; receive anindication of reputation information about the network destination;identify, based at least in part on the received indication ofreputation information, the executable file as malware, wherein theidentification includes a determination of whether the receivedindication of reputation information indicates that the networkdestination is associated with malware; and responsive to theidentification of the executable file as malware, take at least one ofthe following actions to protect the electronic device from the malware:block, clean, quarantine, or remove the executable file.
 3. The mediumof claim 2, wherein the identity information of the network destinationassociated with the executable file provided over the network furtherincludes an Internet Protocol (“IP”) address of the network destination.4. The medium of claim 2, wherein the identification further includes adetermination of whether the network destination matches a URL in awhitelist of sites known to be safe.
 5. The medium of claim 2, whereinthe identification further includes a determination of whether thereceived indication of reputation information indicates that the networkdestination previously hosted other applications with maliciousreputation.
 6. The medium of claim 2, wherein the processor is furthercaused to send a log of information to a reputation server, the log toinclude an Internet Protocol (“IP”) address of the network destinationand information of the executable file.
 7. The medium of claim 2,wherein the identification further includes a determination of whetherthe received indication of reputation information indicates that thenetwork destination is referred by another network destination with amalicious reputation.
 8. A method for security, comprising; identifyingan executable file to reside in at least a portion of memory of anelectronic device; providing, over a network, identity information of anetwork destination associated with the executable file, the identityinformation to include a uniform resource locator (“URL”) of the networkdestination; receiving an indication of reputation information about thenetwork destination; identifying the executable file as malware based atleast in part on the received indication of reputation information,including determining whether the received indication of reputationinformation indicates that the network destination is associated withmalware; and responsive to the identification of the executable file asmalware, taking at least one of the following actions to protect theelectronic device from the malware: block, clean, quarantine, or removethe executable file.
 9. The method of claim 8, wherein the identityinformation of the network destination associated with the executablefile provided over the network further includes an Internet Protocol(“IP”) address of the network destination.
 10. The method of claim 8,wherein identifying the executable file as malware further includesdetermining whether the network destination matches a URL in a whitelistof sites known to be safe.
 11. The method of claim 8, whereinidentifying the executable file as malware further includes determiningwhether the received indication of reputation information indicates thatthe network destination previously hosted other applications withmalicious reputation.
 12. The method of claim 8, further comprisingsending a log of information to a reputation server, the log includingan Internet Protocol (“IP”) address of the network destination andinformation of the executable file.
 13. The method of claim 8, whereinidentifying the executable file as malware further includes determiningwhether the received indication of reputation information indicates thatthe network destination is referred by another network destination witha malicious reputation.
 14. An apparatus, comprising: a processor; atleast one machine accessible storage medium communicatively coupled tothe processor; a monitor module including instructions stored on themedium, the instructions, when executed by the processor, configure themonitor module to: identify an executable file to reside in at least aportion of memory of the apparatus; provide, over a network, identityinformation of a network destination associated with the executablefile, the identity information to include a uniform resource locator(“URL”) of the network destination; receive an indication of reputationinformation about the network destination; identify, based at least inpart on the received indication of reputation information, theexecutable file as malware, wherein the identification includes adetermination of whether the received indication of reputationinformation indicates that the network destination is associated withmalware; and responsive to the identification of the executable file asmalware, take at least one of the following actions to protect theapparatus from the malware: block, clean, quarantine, or remove theexecutable file.
 15. The apparatus of claim 14, wherein the monitormodule is further configured to provide an Internet Protocol (“IP”)address of the network destination in the identity information of thenetwork destination associated with the executable file provided overthe network.
 16. The apparatus of claim 14, wherein the monitor moduleis further configured to identify the executable file as malware furtherbased on a determination of whether the network destination matches aURL in a whitelist of sites known to be safe.
 17. The apparatus of claim14, wherein the monitor module is configured to identify the executablefile as malware further based on a determination of whether the receivedindication of reputation information indicates that the networkdestination previously hosted other applications with maliciousreputation.
 18. The apparatus of claim 14, wherein the monitor module isfurther configured to send a log of information to a reputation server,the log to include an Internet Protocol (“IP”) address of the networkdestination and information of the executable file.
 19. The apparatus ofclaim 14, wherein the monitor module is configured to identify theexecutable file as malware further based on a determination of whetherthe received indication of reputation information indicates that thenetwork destination is referred by another network destination with amalicious reputation.
 20. At least one machine accessible storage mediumhaving code stored thereon, the code, when executed on an electronicdevice, to cause the electronic device to: receive, over a network,identity information of an executable file to reside in at least aportion of memory of a client, the identity information including auniform resource locator (“URL”) of a network destination associatedwith the executable file; access reputation information about thenetwork destination in a reputation database; and send an indication ofthe reputation information about the network destination to the clientto identify the executable file as malware, wherein the indication ofthe reputation information: indicates that the network destination isassociated with malware; and indicates that that the executable file isto be blocked, cleaned, quarantined, or removed.
 21. The medium of claim20, wherein: the identity information of the network destinationassociated with the executable file provided over the network furtherincludes an Internet Protocol (“IP”) address of the network destination;and the reputation information about the network destination in thereputation database is accessed using at least the IP address of thenetwork destination.
 22. The medium of claim 20, wherein the indicationof the reputation information about the network destination includes adetermination of whether the network destination matches a URL in awhitelist of sites known to be safe.
 23. The medium of claim 20,wherein: the electronic device is further caused to determine from thereputation information whether the network destination previously hostedother applications with malicious reputation; and the indication of thereputation information about the network destination includes thedetermination of whether the network destination previously hosted otherapplications with malicious reputation.
 24. The medium of claim 20,wherein the electronic device is further caused to: receive a log ofinformation, the log to include an Internet Protocol (“IP”) address ofthe network destination and information of the executable file; andupdate the reputation information of the network destination based uponthe log.
 25. The medium of claim 20, wherein: the electronic device isfurther caused to determine from the reputation information whether thereceived indication of reputation information indicates that the networkdestination is referred by another network destination with a maliciousreputation; and the indication of the reputation information about thenetwork destination includes the determination of whether the receivedindication of reputation information indicates that the networkdestination is referred by another network destination with a maliciousreputation.
 26. A method for security, comprising: receiving, over anetwork, identity information of an executable file to reside in atleast a portion of memory of a client, the identity informationincluding a uniform resource locator (“URL”) of a network destinationassociated with the executable file; accessing reputation informationabout the network destination in a reputation database; and sending anindication of the reputation information about the network destinationto the client to identify the executable file as malware, wherein theindication of the reputation information: indicates that the networkdestination is associated with malware; and indicates that that theexecutable file is to be blocked, cleaned, quarantined, or removed. 27.The method of claim 26, wherein: the identity information of the networkdestination associated with the executable file provided over thenetwork further includes an Internet Protocol (“IP”) address of thenetwork destination; and the reputation information about the networkdestination in the reputation database is accessed using at least the IPaddress of the network destination.
 28. The method of claim 26, whereinthe indication of the reputation information about the networkdestination includes a determination of whether the network destinationmatches a URL in a whitelist of sites known to be safe.
 29. The methodof claim 26: further comprising determining from the reputationinformation whether the network destination previously hosted otherapplications with malicious reputation; and wherein the indication ofthe reputation information about the network destination includes thedetermination of whether the network destination previously hosted otherapplications with malicious reputation.
 30. The method of claim 26,further comprising: receiving a log of information, the log to includean Internet Protocol (“IP”) address of the network destination andinformation of the executable file; and updating the reputationinformation of the network destination based upon the log.
 31. Themethod of claim 26: further comprising determining from the reputationinformation whether the received indication of reputation informationindicates that the network destination is referred by another networkdestination with a malicious reputation; and wherein the indication ofthe reputation information about the network destination includes thedetermination of whether the received indication of reputationinformation indicates that the network destination is referred byanother network destination with a malicious reputation.
 32. Anapparatus, comprising: a processor; at least one machine accessiblestorage medium communicatively coupled to the processor; a reputationmodule including instructions stored on the medium, the instructions,when executed by the processor, configure the reputation module to:receive, over a network, identity information of an executable file toreside in at least a portion of memory of a client, the identityinformation including a uniform resource locator (“URL”) of a networkdestination associated with the executable file; access reputationinformation about the network destination in a reputation database; andsend an indication of the reputation information about the networkdestination to the client to identify the executable file as malware,wherein the indication of the reputation information: indicates that thenetwork destination is associated with malware; and indicates that thatthe executable file is to be blocked, cleaned, quarantined, or removed.33. The apparatus of claim 32, wherein: the identity information of thenetwork destination associated with the executable file provided overthe network further includes an Internet Protocol (“IP”) address of thenetwork destination; and the reputation information about the networkdestination in the reputation database is accessed using at least the IPaddress of the network destination.
 34. The apparatus of claim 32,wherein the indication of the reputation information about the networkdestination includes a determination of whether the network destinationmatches a URL in a whitelist of sites known to be safe.
 35. Theapparatus of claim 32, wherein: the reputation module is furtherconfigured to determine from the reputation information whether thenetwork destination previously hosted other applications with maliciousreputation; and the indication of the reputation information about thenetwork destination includes the determination of whether the networkdestination previously hosted other applications with maliciousreputation.
 36. The apparatus of claim 32, wherein the reputation moduleis further configured to: receive a log of information, the log toinclude an Internet Protocol (“IP”) address of the network destinationand information of the executable file; and update the reputationinformation of the network destination based upon the log.
 37. Theapparatus of claim 32, wherein: the reputation module is furtherconfigured to determine from the reputation information whether thereceived indication of reputation information indicates that the networkdestination is referred by another network destination with a maliciousreputation; and the indication of the reputation information about thenetwork destination includes the determination of whether the receivedindication of reputation information indicates that the networkdestination is referred by another network destination with a maliciousreputation.